Columbia Kermit/kermit.zip/newsgroups/misc.19950329-19950528/[e-mail]_Fri Apr 28 20:23:43 1995.msg

Internet Message Format | 2020-01-01 | 2KB

Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA11596
  (5.65c+CU/IDA-1.4.4/HLK for <[e-mail]>); Fri, 28 Apr 1995 16:23:52 -0400
Received: by apakabar.cc.columbia.edu id AA19774
  (5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Fri, 28 Apr 1995 16:23:50 -0400
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: [e-mail] (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Using Kermit as an DLL
Date: 28 Apr 1995 20:23:43 GMT
Organization: Columbia University
Lines: 17
Message-Id: <3nrisf$[e-mail]>
References: <3nq072$[e-mail]>
Nntp-Posting-Host: watsun.cc.columbia.edu
Apparently-To: [e-mail]

In article <3nq072$[e-mail]>,  <[e-mail]> wrote:
:I'm developing an application that is doing som file transfer in the
:background and I'm today using the Kermit protocol for this.
:
:The 'problem' is that I would like to use Kermit as ordinary function calls
:using DLL's instead of starting it as an .exe file!
:
There is no Kermit DLL.  Although you might prefer to have a DLL, those of
us who do the work would prefer it if you used the tools at hand, such as
KERLITE.EXE, with the normal licensing terms if you are creating a commercial
product or otherwise furnishing software to customers or clients, etc, for
commercial gain and/or advantage.  This way, you get the best Kermit
implementation available, and we get some income to pay for our continued
existence and further development.  Send email to [e-mail] to
discuss this further.

- Frank